As long ago as 2009, Apple knew which way the wind was blowing with its there’s an app for that TV advertising campaign. All these years on, the world has gone well and is truly mobile-first. Having a mobile app for your business seems a no-brainer. There are, though, some points you need to keep in mind from the outset if the app is going to deliver real value to both you and your customer.

A clear purpose

MBA textbooks are littered with sad tales of amazing solutions that foundered for want of a problem they could solve. Developing an app because you need an app is no reason at all. Approach the question from a jobs-to-be-done perspective and you’re less likely to fall into any rabbit holes. What does your customer want or need right now to make life better or easier, and how is the mobile app you are developing instrumental in meeting that needs or doing that job?

Regulatory requirements

If your business operates in a highly regulated market, you'll need to factor that into your thinking every step of the way. The iGaming sector is a good example - you'll see this provider has a specific online casino app in Pennsylvania that is different from the one in New Jersey due to specific state regulations that have to be met. This example also touches on the need to explore whether you need to incorporate hyperlocal, regional or national distinctions into the app under development.

Design and UX

Don’t underestimate the importance of design with a mobile app. People tend to be more forgiving with desktop software and will make allowances if something is otherwise up to the job. In the mobile world, it’s another matter. People get highly emotional about installing mobile apps and then regretting it. It’s something that would make a fascinating psychological study, but that’s for another day. For current purposes, it’s better to simply remain stoic and do everything we can to avoid poor UX in the first place.

Start with the MVP

No, that’s not the most valuable player, it’s the minimal viable product. We’ve mentioned already that it’s easy to get carried away adding functionality that is nice to have but does not exactly add value. By first developing an MVP, you are encouraged to start with the basics and work up. It means a better likelihood of being right the first time on meeting minimum requirements, and then of adding only such functionality as your customer wants to get the job done even better.

Get everyone on board early

Designing an app that adds value is a collaborative task, and if you get the development team involved from day one, the overall journey will be easier and more efficient. They will be the people who can steer you away from blind alleys and avoid wasting time on multiple prototypes. They are also in an ideal position to advise objectively on fundamental questions like the underlying software and the basic user interface.